🤖 I have created a release *beep* *boop*
---


##
[1.11.0](launchdarkly_common_client-v1.10.0...launchdarkly_common_client-v1.11.0)
(2026-06-03)


### Features

* Wire FDv2 connection-mode resolution in common_client
([#279](#279))
([ceb931f](ceb931f))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Version and changelog/manifest updates only; no runtime code changes
in this PR.
> 
> **Overview**
> Release Please PR that **bumps** `launchdarkly_common_client` from
**1.10.0** to **1.11.0** and syncs the release manifest
(`.release-please-manifest.json`).
> 
> The **CHANGELOG** entry for 1.11.0 documents the shipped feature from
[#279](#279):
wiring **FDv2 connection-mode resolution** in common_client (building on
the FDv2 connection/resolved-mode types added in 1.10.0). **No
application or library source changes** appear in this diff—only version
and release notes.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
2c1d100. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

## Summary

Wires the FDv2 mode-resolution machinery into the Flutter SDK's
`ConnectionManager`. Stacked on the common_client PR (#279); rebase onto
`main` once that merges.

This is the second half of the further split of the original behavior PR
(#275, now closed).

**ConnectionManager**
- `DartClientAdapter` forwards `ResolvedConnectionMode` to
`LDCommonClient.setResolvedMode` (the new advanced FDv2 entry point from
#279).
- `ConnectionManagerConfig.backgroundConnectionMode` (new) is typed
`FDv2ConnectionMode`. `initialConnectionMode` stays `ConnectionMode`
(legacy).
- `disableAutomaticBackgroundHandling` keeps its original name.
- Automatic mode resolution uses `resolveMode` +
`flutterDefaultResolutionTable`; `setMode` override path supports the 3
FDv1 modes only (background is auto-resolved, not user-selectable).

**Flutter umbrella re-exports** cover the FDv2 types consumed by this PR
(`FDv2ConnectionMode` + four subtypes, `ResolvedConnectionMode` family,
`OfflineDetail` family,
`ModeState`/`ModeResolutionEntry`/`resolveMode`/`flutterDefaultResolutionTable`).

**Platform defaults** (`io_config` / `js_config` / `stub_config` /
`flutter_default_config`) return `FDv2ConnectionMode` for the background
slot.

**LDClient** passes `backgroundConnectionMode` to the
`ConnectionManager` and sets `offline=true` post-construction (no longer
forces initial mode to offline in config).

Tests updated to match.

**Depends on** #279 -- the `LDCommonClient.setResolvedMode` method this
PR consumes lives there.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Connection and data-source behavior changes across
foreground/background and network transitions (including new status
reasons and mobile background polling), which can affect flag freshness
and event delivery even though public FDv1 `setMode` remains.
> 
> **Overview**
> **Flutter `ConnectionManager`** now picks a
**`ResolvedConnectionMode`** from app foreground/background, network,
config, and optional overrides using **`resolveMode`** and
**`flutterDefaultResolutionTable`** (custom tables supported). It
forwards modes through **`DartClientAdapter.setResolvedMode`**, adds
**`backgroundConnectionMode`**, and **`setMode(FDv2ConnectionMode?)`**
for manual override. Background transitions still **flush** events;
event sending rules are tied to offline / background +
**`runInBackground`**.
> 
> **`common_client`** **`DataSourceManager`** is keyed on
**`FDv2ConnectionMode`** factories and
**`setMode(ResolvedConnectionMode)`**, mapping offline
**`OfflineDetail`** to **`setOffline` / `setNetworkUnavailable` /
`setBackgroundDisabled`**. **`LDCommonClient`** composes FDv1 factories
into FDv2 (including an SDK-managed **background polling** factory),
exposes **`setResolvedMode`**, and stops pushing network availability
into the data source manager (Flutter resolves network loss to
**`ResolvedOffline(OfflineNetworkUnavailable)`** instead).
> 
> **Platform defaults**: mobile uses **`FDv2Background`** and enables
automatic background/network handling by default; desktop and web
default the background slot to offline and disable those detectors
unless configured. **`LDClient`** passes the platform background slot
and sets **`ConnectionManager.offline`** after build when
**`config.offline`**. FDv2 types are re-exported from the Flutter
package; **`launchdarkly_common_client`** is bumped to **1.11.0**.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
bc0a1ac. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->